Synchronize writes across all instances of ConsoleSink #65
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, each instance of
ConsoleSink
is synchronized so that concurrent output is not interleaved.Some scenarios, like reinitialization of the logging pipeline, non-singleton loggers, and Serilog.Sinks.Map can result in multiple instances of
ConsoleSink
being constructed, and today these will happily interleave output. (E.g. see serilog/serilog#1350 .)This PR switches the lock from sink-specific to shared, so that at least all writes through console sinks will be non-interleaved (even if other console output isn't controlled this way).
CC @skomis-mm